Repository navigation
feat(sdk): update hotdata SDK to 0.23.0 and surface rollups - #372
Merged
Merged
Conversation
- Bump the hotdata SDK from 0.21.0 to 0.23.0. - jobs list --job-type accepts rollup_build and rollup_refresh_sweep. - queries <id> shows whether a rollup answered the query (rollup field in json/yaml, a rollup line in the detail view).
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Updates the
hotdataSDK from 0.21.0 to 0.23.0 and surfaces what the new SDK exposes for rollups.jobs list --job-typeacceptsrollup_buildandrollup_refresh_sweep.databases queries <id>shows whether a rollup answered the query: arollupfield injson/yamloutput (used,not_ready,not_matched,unavailable, or null) and arollup:line in the detail view.Not changed
hotdata querykeeps its current request flow. The SDK's newClient::query_arrowis a synchronous call and rejectsasyncrequests, while the CLI submits withasync+async_after_msso that long queries fall back to a query run it can poll (and thatquery statuscan resume). Results already stream as Arrow.Tests
rollupmapping.queryinjson,csvandtable(including the capped-table exit code 3),--dialect clickhouse, a 300,000-row result,jobs list --job-type rollup_build, anddatabases queries <id> -o json.